Smart synthesizer system

ABSTRACT

Methods, systems, and apparatus, including computer programs encoded on computer storage media for generating a patient profile. One method includes generating a patient profile corresponding to a patient that comprises profile data items and profile data parameters. Generating a synthesized context-aware rendition of a patient summary from the profile data items and the profile data parameters. Mapping doctor specialties and data workflows in relation to the synthesized context-aware rendition of the patient summary.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority under 35 U.S.C. § 119 to Indian PatentApplication No. 201621041462, filed on Dec. 5, 2016, which contents ishereby incorporated by reference in its entirety.

BACKGROUND

This specification relates generally to the field of informationsystems, computational systems, databases, networking systems, andcommunication systems.

SUMMARY

This specification relates to the field of healthcare information,healthcare technology, healthcare management, electronic medicalrecords, electronic health records, decision support systems and patientcentered care.

Medical practice entails activities in relation to human health andbody, understanding and diagnosing various factors affecting humanhealth and body, surgical procedures, examination procedures, diagnosticprocedures, prognosis procedures, and similar activities. Qualifiedmedical professionals are equipped to deal with various facets ofmedical practice; in relation to the academic qualification that theyhave reached, and in relation to the professional experience that theyhave gained.

The terms medical record, health record, encounter and medical chart areused somewhat interchangeably to describe the systematic review anddocumentation of a single patient's medical or health journey includinga patient's history, diagnosis, prognosis, symptoms, vitals, review ofsystems, physical examination, medications, lab and diagnostics,allergies, surgical procedures and care. These factors include acrosstime not just within one particular health care provider setting, butalso covering multiple health care providers and the multiple healthcare providers' interactions with the respective patient in context.

Medical records include a variety of notes and data relating todoctor-patient interaction, doctor's interpretation of patient'scomplaints, diagnosis, prognosis, investigations and treatment plans.This data could include signs and symptoms data, review of various bodysystems data, examination data, vitals data, diagnosis data, medicaldecision making data, medical history data, family history, socialhistory, previous surgical procedures and hospitalizations, any specifichistorical data of medicines taken, allergies, chronic and acuteproblems, lab reports, radiology images and reports' data, otherinvestigation results' data, input/output data, and drugs andimmunization administration data and medication data. In addition, thisdata can include prognosis data, visit notes, insurance data,demographics, other relevant health histories, genomic data, data fromwearables and other medical devices, and other similar types of data. Assuch, it is essential for both the doctor and the patient to review andmaintain complete and accurate medical records for ensuing accuratediagnosis and treatment also from a general health perspective, awellness perspective, and a legal perspective.

Medical records are used to understand the patient's current healthstatus and past health history to ensure patient wellness. In addition,a doctor may review medical records to identify patient's diagnosis andprovide/recommend relevant treatment protocols to a patient or fellowcare providers for treating patients. Medical records can also be usedas an aid to supplement the judgement and decision of a doctor/careprovider. Medical records are also used in a system to capture data of apatient at various stages of his/her life and is used for a variety ofmedical and analytical purposes.

The types of personal health information that can be included in themedical records may cover the following: patient demographicsinformation including, but not limited to, name, gender, birth date,blood type, race, ethnicity, marital status, address/geographicallocation, emergency contact information; complete history of patientspast visit histories; date of last physical exam; dates and results oftests and screenings; major illnesses and surgeries, with dates; a listof medicines, dosages and how long they are being taken; any allergiesand its reactions; any chronic/acute diseases and treatment plans; anyhistory of illnesses in your family; dates and results of lab tests,imaging tests, and screenings; social history, family history;immunizations; risk assessments; care plans; vitals; data fromwearables; genomic data; and, various clinical assessments and scores.

In general, one innovative aspect of the subject matter described inthis specification can be embodied in methods that include the actionsof generating a patient profile corresponding to a patient thatcomprises profile data items and profile data parameters. Generating asynthesized context-aware rendition of a patient summary from theprofile data items and the profile data parameters. Mapping doctorspecialties and data workflows in relation to the synthesizedcontext-aware rendition of the patient summary.

Other embodiments of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.For a system of one or more computers to be configured to performparticular operations or actions means that the system has installed onit software, firmware, hardware, or a combination of them that inoperation cause the system to perform the operations or actions. For oneor more computer programs to be configured to perform particularoperations or actions means that the one or more programs includeinstructions that, when executed by data processing apparatus, cause theapparatus to perform the operations or actions.

The foregoing and other embodiments can each optionally include one ormore of the following features, alone or in combination. In particular,one embodiment includes all the following features in combination. Insome implementations, the method includes, determining weightingassignments in relation to a context. In response to determining theweighting assignments in relation to the context, assigning weights tothe profile data items, the profile data parameters, andknowledge/reference data items. The method can further include whereindetermining the weighting assignments is determined based on a frequencyof use, a latest use, determination of various heat maps to understandusage and behavior, location, specialty, and current condition of thepatient.

The method can further include generating an interactive time-line viewfor a doctor-patient interaction from an observation profile. The methodcan further include wherein the observation profile changes in vitals,inputs, outputs in response to change in dosage of prescribed medicine,in response to change in filtering parameters for labs, vitals, anddiagnostics. The method can further include determining a location of adoctor corresponding to the patient profile assessing a smartsynthesizer system, wherein factors in determining the location of thedoctor include care settings, seasons, external conditions, andseriousness of the condition of the patient.

The method can further include, storing, in an information database,journal information relating to diseases and treatment plans for thediseases, and case studies' information relating to the disease andtreatment plans. The method can further include displaying, on theinteractive time-line view, the changes in vitals, intake output, labs,or similar data in an empirical format and a predictive format.

The details of one or more embodiments of the subject matter of thisspecification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of the smart synthesizer system.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

A care management system typically includes comprehensive medicalrecords of patients and set of procedures and protocols that a doctorprescribes for a patient. In its electronic format, patient centeredelectronic medical record systems involve all the aspects of patient andillness/disease management, steps pertaining to which are describedabove and may generally be referred to during a patient-doctorinteraction or for treating patients or for evolving better treatmentprotocols for future patients. For a doctor to review and record allaspects or facets of a patient, during the doctor-patient interaction,it is imperative that such patient centered electronic medical recordsystems be intuitive towards the workflows of that particular doctor andkeep in context the various aspects of patient's demographic and medicalinformation. It is imperative that these systems provide patient medicalinformation views to clinicians such that they spend as little time aspossible to find relevant information to ensure better diagnosis andmedical decision making for treatment protocols and document importantfacets of the patient's encounter, and focus more on patient care asmuch as possible. Intuitiveness in this case means the ability of thesystem to understand how a clinician practices, learn from how theclinician practices, and be able to provide the right workflow, so thatthe clinician does not waste time in searching for information relevantin the context of the patient and his/her history and for documenting apatient record.

Typically, a patient can be profiled in terms of demographics, medicalhistory, family history, social history, current context (relating toseason, epidemic, travel history, and the like), previous surgeries'history, investigations, vitals, current and previous problems,allergies, immunizations, and the like.

In at least one context of patient centered electronic medical recordsystems, a ‘doctor-patient interaction’ is meant to include the steps ofunderstanding patient reported complaints, reviewing patient's medicalrecords in the context of the complaints and condition, documentinghistory of present illnesses, to reviewing of body systems, to doingphysical examination of the patient, and to diagnosis to treatment planto prognosis. In this context, it is important that the system used incorrelation with this doctor-patient interaction is ready to‘understand’ the interaction.

In some implementations, it is important that the system iscontext-aware so that it understands the doctor correctly in terms ofpre-defined parameters.

In some implementations, it is important that the system iscontext-aware so that the system understands the patient correctly interms of pre-defined parameters.

In some implementations, it is important that the system iscontext-aware so that it understands the patient's previous records andhistories correctly in terms of pre-defined parameters.

In some implementations, it is important that the system iscontext-aware so that it understands the doctor-patient interactioncorrectly in terms of pre-defined parameters.

In some implementations, it is important that the system iscontext-aware so that it understands the location and seasons correctlyin terms of pre-defined parameters.

In some implementations, it is important that the system iscontext-aware so that it understands the demographic correctly in termsof pre-defined parameters.

In some implementations, it is important that the system iscontext-aware so that it understands how the doctor is interacting withthe patient, reviewing medical records and documenting in the patientcentered electronic medical record system in terms of pre-definedparameters.

In some implementations, it is important that the system iscontext-aware so that it understands the current condition or state ofthe patient while documenting in the patient centered electronic medicalrecord system in terms of pre-defined parameters.

In some implementations, it is important that the system iscontext-aware so that it understands which data set (ex vitals, labresults, etc.) of the medical record should be promoted of the patientwhile reviewing patient medical records and documenting in the patientcentered electronic medical record system in terms of pre-definedparameters.

In some implementations, it is important that the system iscontext-aware so that it understands which actions (e.g. add aparticular problem, suggest a particular test, etc.) of the medicalrecord should be promoted of the patient while documenting in thepatient centered electronic medical record system in terms ofpre-defined parameters.

It is important that an intelligent and intuitive system and method beconfigured and designed so that a doctor is enabled and empowered tointeract with the system in a context-aware manner. Therefore, there isa need to make the system and method context-aware and context-ready fora doctor to interact with it.

With the advent of Internet of Things (JOT) and mobility, wearabledevices and sensors have become ubiquitous in nature. Doctors today arefacing issues with understanding contexts from trillions of bytes ofinformation that they receive from their patients. The vastness of thisdata needs to be interpreted by intelligent systems, and has to bepresented to a doctor in a manner, which will make logical sense fordecision-making. This intelligent system needs to be aware of variouscontexts in which these datasets were captured by these devices. Thosecontexts need to be interpreted in real time to aid the doctor to nottake unnecessary interventions or measures, which will increasehealthcare costs.

Also, each doctor has his/her own way of practicing and consumingpatient data. The data needs to communicate to the doctor, what answershe/she is looking for to take real time decisions at point-of-care. Thismethod of synthesizing data with various contexts and presenting it tothe doctor is one of the premises of this specification.

For example, a neurologist taking a round at an NICU to see a mid-agedmale trauma patient, and sees his last 24 hours of vitals, then reviewslast updated lab results, searches for a particular medication order,and sees what happened to vitals post that medication, looks for nursingnotes to find any adverse events, and then goes to documenting theencounter. The machine can detect these types of patterns, and then thedata could be synthesized for this doctor, for this type of patientswith similar contexts and presented to the doctor to take quick andeffective decisions.

In another example, a 19 year old lady with a kid—unmarried—history ofabortion and abuse comes to the ER at a hospital, the system shouldautomatically take into account risks associated and provide riskstratification in terms of suggesting to perform at least certain testsrelating to abuse, abortion—etc.

In some implementations, the system should automatically pick upvariations in the data or changes in the pattern of synthesis of dataand compare those against what was expected and presented is upfront tothe doctor to take actions, rather than the doctor figuring out theissue and treating reactively.

An object of the invention is to provide a system and method to providea system for electronic medical and health records.

Another object of the invention is to provide a system and method forelectronic medical and health records, which aids a doctor inidentifying and quickly reviewing correct medical information and italso aids doctor to take decisions (computer-aided decisions) with apatients profile including profile fields, which relate tons, weights,measurements, centered around the patient's electronic medical record.

Yet another object of the invention is to provide a system and method toimprove health care quality.

Still another object of the invention is to provide a system and methodfor recording at least a facet of doctor-patient interaction/visit.

An additional object of the invention is to provide a system and methodfor providing a touch based, click based, voice based or gesture basedrecording of at least a facet of doctor-patient interaction/visit.

Yet an additional object of the invention is to provide an intuitivesystem and method for recording a doctor-patient interaction/visit.

Still an additional object of the invention is to provide an intelligentsystem and method for recording a doctor-patient interaction/visit.

Another additional object of the invention is to provide a system andmethod, which is context aware so that it understands a doctorcorrectly, in relation to a doctor-patient interaction, in terms ofpre-defined parameters.

Yet another additional object of the invention is to provide a systemand method so that it understands the patient correctly, in relation toa doctor-patient interaction, in terms of pre-defined parameters.

Still another additional object of invention is to provide a system andmethod so that it understands the patient's current and previous medicalrecords and histories correctly in terms of pre-defined parameters.

Yet another additional object of the invention is to provide a systemand method so that it understands the doctor-patient interactioncorrectly in terms of pre-defined parameters.

Yet an additional object of the invention is to provide a system andmethod so that it understands the location correctly, in relation to adoctor-patient interaction, in terms of pre-defined parameters.

Still an additional object of the invention is to provide a system andmethod so that it understands the demographic correctly, in relation toa doctor-patient interaction, in terms of pre-defined parameters.

Yet an additional object of the invention is to provide a system andmethod so that it understands how the doctor is interacting with thepatient and documenting in the patient centered electronic medicalrecord system in terms of pre-defined parameters.

Yet an additional object of the invention is to provide a system andmethod so that it understands how the doctor is interacting with thepatient and ordering in the patient centered electronic medical recordsystem in terms of pre-defined parameters.

Still another additional object of the invention is to provide a systemand method so that it understands the current condition or state of thepatient while documenting in the patient centered electronic medicalrecord system in terms of pre-defined parameters.

Yet an additional object of the invention is to provide a system andmethod so that it understands which data set (e.g. vitals, lab results,notes, orders, med administration records, past history, and the like)of the medical record should be promoted of the patient whiledocumenting in the patient centered electronic medical record system interms of pre-defined parameters.

Still another additional object of the invention is to provide a systemand method so that it understands which actions or entities (e.g. add aparticular problem, suggest a particular test, and the like) of themedical record should be promoted of the patient while documenting orordering in the patient centered electronic medical record system interms of pre-defined parameters.

Another additional object of the invention is to provide an intelligentand intuitive system and method to be configured and designed so that adoctor is enabled and empowered to interact with the system in acontext-aware manner.

Yet another object of the invention is to make a system and method, fora doctor-patient interaction, context-aware and context-ready for adoctor to interact with it.

Still another additional object of the invention is to provide a systemand method so that it understands how to render the synthesizedinformation in real time to suit to the doctor's style of practicingwhile documenting in the patient centered electronic medical recordsystem in terms of pre-defined parameters.

An additional object of the invention is to provide a system and method,which is easy to use and understand for doctors as well as for patients,thereby increasing user adaptability.

For the purposes of this specification, the term, ‘doctor’ would includewithout limitations doctor, doctors, physicians, specialists, superspecialists, dentists, surgeons, physiologists, psychiatrists,hospitalists, physiotherapists, medics, medical practitioners, medicos,nurses, nurse practitioners, physician assistants, paramedics, midwifes,clinical staff, and the likes of hospital related or healthcare relatedpersons who deal with patients.

For the purposes of this specification, a ‘tap’ is defined as a touch ora haptic contact or haptic engagement (whether discrete or continuous)or a click or a gesture, in response to which a pre-defined task oraction takes place.

For the purposes of this specification, the term, ‘care management’, ismeant to include actions, set of procedure and protocols adhered in ahealthcare environment, which may include, but is not limited toscheduling, patient registration, patient onboarding, patient relateddocument management, patient account management, billing, claims'processing, illness management, diagnosis, prognosis, examination,tests, results, interconnecting various nodes in the healthcareecosystem, notifications and alarms, and the like.

FIG. 1 illustrates a schematic block diagram of the smart synthesizersystem 100. In some implementations. In some implementations, the smartsynthesizer system 100 includes a profile configuration mechanism (PCM)102 adapted to define, configure, and render a patient profile. Eachpatient profile includes profile fields, which are to be populated withprofile data items and parameters relating to these profile data items,hereinafter called profile data parameters. Each of the profile dataitems are tagged and weighted as per relevant context.

Typically, a patient's profile includes profile fields which relate todemographics, medical history, previous encounters, physicians,problems, diagnosis, allergies, vitals, signs, weights, measurements,growth chart, lines and tubes, intake and output measurements,immunizations and schedule, labs, microbiology, pathology, administeredmedications, home medications, notes (progress notes, nursing notes,other clinically relevant notes), outstanding orders, diagnostic results(reports, images, and the like), code status, respiratory treatment,family history, social history, previous surgical and/or hospitalizationhistory, any other specialty specific history, risk scores, variousassessments, current complaints, adverse reactions, current context(relating to season, epidemic, location, travel, genetics, race,ethnicity and the like), discharge summaries, visit summaries, genomicdata of the patient, role of a user, department and specialty, caresetting, and the like important event notifications.

In some implementations, each of these profile items corresponds to acontext, which is further used in this system and method in order tosynthesize a context-aware rendition of patient summary.

In some implementations, the smart synthesizer system 100 includes a setof knowledge/reference databases (KDB) 108. This set ofknowledge/reference databases 108 includes multiple fields, which arepopulated. These fields are knowledge/reference fields. Theseknowledge/reference fields correlate with profile fields in one or moreways. Data in these knowledge/reference fields refer toknowledge/reference data items. The knowledge/reference fields as wellas knowledge/reference data items are updateable as and how the systemand method iteratively learns, using artificial intelligence, real timedata capture from doctor patient interactions, machine-learningtechniques pertaining to a doctor and/or the doctor-patientinteraction/visit. Further, these knowledge/reference data items areused to ‘synthesize’ the existing knowledge/reference data items inorder to obtain synthesized knowledge/reference databases 110 in orderto render them in a correlation fashion in synchronism with ‘profilefields’ such that ‘rendered’ profile data items are obtained and servedas an output.

In some implementations, each of the profile data fields are correlatedwith knowledge/reference fields.

In some implementations, the knowledge database, data items may includeinputs from journals, websites, case studies, previous medical records,clinical trials, evidence based medicine data, clinical decision supportsystem related data, population health data, and the like. Initially,these data items are structured using pre-defined rules of structuringand association in relation with pre-defined structured matrices such asUMLS or SNOMED terminologies. These rules are auto-learned, auto-updatedintelligently, over time. Various aspects of Natural Language Processingand Machine Learning techniques are used to create these knowledgedatabases. NLP is used to break down text (e.g. data from journals,textbooks, articles, case studies, previous medical records, webmaterial, data from wearables, sensors, IoT devices, other medicaldevices, patient medical records, physician documentation/notes and thelike) into various forms of data items like conditions, problems,findings, symptoms, medications, allergies, medical equipment, medicalevents, procedures, orders and the like and then are referenced,indexed, tagged, with cross-references with other data items.

In some implementations, the smart synthesizer system 100 includes aspecialty-specific mapping mechanism 112 configured to map doctorspecialties and their clinical and data workflows in relation with theset of the synthesized knowledge/reference databases 110. In someimplementations, the specialty-specific mapping mechanism 112 readsinput items from a pre-determined specialty database and correlativelysynthesizes the synthesized knowledge/reference databases 110 intospecialty-specific synthesized knowledge/reference databases 114. Thisis done by a mechanism wherein pertinent fields of specialty are picked,weight-assigned, and thereby mapped.

In some implementations, the set of specialty-specific synthesizedknowledge/reference databases 114 includes specialty mapped databases,characterized, in which, at least a database includes fields and dataitems that are contextually relevant to a pre-defined specialty. Manysuch pre-defined specialty-specific databases can be built which havecorrelating specialty-specific fields and specialty-specific data items.

In some implementations, the smart synthesizer system 100 includes aweight assignment mechanism 104 that is configured to assign weights toitems in a set consisting of profile fields, profile data items, profiledata parameters, knowledge/reference data items and the like. Theseweights are dynamic in nature. Weights assignment is determined inrelation to determined context. Depending upon weight assignment, aprofile is rendered. Weight assignment is sought by determination offrequency of use, a latest use, determination of various heat maps usedto understand usage and behavior, context settings like location,specialty, current condition of the patient, current of frequency anduse of profile data items and/or knowledge/reference data items and thelike.

In some implementations, the smart synthesizer system 100 includes arendering mechanism 106 that is configured to render the system in acontext-aware view for a doctor-patient interaction based on pre-definedinputs. Only context relevant data is rendered.

In some implementations, for a given patient profile, the renderingmechanism 106 renders a version of this system and method which ispertinent to the doctor in terms of at least an input selected fromasset of inputs consisting of location related inputs, disease relatedinputs, patient profile related inputs, doctor profile related inputs,specialty related inputs, and the like.

Furthermore, the rendering mechanism 106 may render a version of thissystem with similar patients with similar signs, symptoms, complaints,disease group, demographics, or previous history.

Furthermore, the rendering mechanism 106 may render an interactivetime-line view of this system for a doctor-patient interaction. In someimplementations, the rendering mechanism 106 is configured to render anobservation profile, which is a function of inputs from the profileconfiguration mechanism, the set of specialty-specific synthesizedknowledge/reference databases, and weight assignment mechanism 104.

In some implementations, an observation profile includes changes invitals, inputs, outputs in response to change in dosage of prescribedmedicine, in response to change in filtering parameters for labs,vitals, diagnostics, and the like. In this embodiment, dosage values forpatient are obtained from the patient profile configuration mechanism,standard laboratory values are obtained from the specialty-specificsynthesized knowledge/reference databases 114, instantaneous values areobtained from a doctor-patient interaction correlating to the patientprofile configuration mechanism. In response to these inputs, therendering mechanism 106 is configured to assign weights in relation to adetermined context and display changes in vitals, intake output, labs orsimilar data in an empirical format as well as in a predictive format.

In some implementations, the rendering mechanism 106 is configured torender a paraphrased note, which is a function of inputs from theprofile configuration mechanism, the set of specialty-specificsynthesized knowledge/reference databases 114, and weight assignmentmechanism 104 along with natural language processing. In someimplementations, a doctor-patient interaction can be converted into aparaphrased note and into actionable items using natural languageprocessing.

In some implementations, the rendering mechanism 106 is configured torender a discharge summary, which is a function of inputs from theprofile configuration mechanism, the set of specialty-synthesizedknowledge/reference databases 114, and weight assignment mechanism 104in relation to a doctor-patient interaction. In some implementations, adischarge summary relates to pertinent data of a patient.

In some implementations, the rendering mechanism 106 includes afiltering mechanism in order to filter out and retain data based onstructure relationships and artificial intelligence pertaining tocontext awareness and doctor profile and doctor behavior.

In some implementations, the pre-defined inputs are selected from a setof inputs consisting of defined patient profile, defined doctorspecialty, doctor location, patient location, defined doctor profile,and the like. Additional inputs may be defined in order to make thissystem and method more intelligent.

In some implementations, the profile defining mechanism is correlated toan exodus dataset configured to store exodus data. Additionally, theprofile defining mechanism is correlated to a genomic dataset configuredto store genomic data.

In some implementations, the smart synthesizer system 100 includes aninformation database that is configured to store journal informationrelating to diseases and treatment plans, case studies' informationrelating to diseases and treatment plans. Each aspect of information inthe information database is parsed to be broken down into items ofcontent. These items of content can be data or metadata and are madeavailable to be associated or correlated with various other database andprocessing or rendering mechanisms of this system.

In some implementations, the smart synthesizer system 100 includes adoctor location determination mechanism that is configured to identifylocation of a doctor assessing the smart synthesizer system 100.Typically, this is a relation to a doctor-patient interaction/visit.These locations factor in type of care settings, seasons, externalcondition, seriousness of the condition of the patient, and the like.

In some implementations, the smart synthesizer system 100 includes atleast a database relating to evidence based guidelines. Typically, thisdatabase includes or correlates to at least a database relating totreatment protocols. In addition, additionally, this database includesor correlates to at least a database relating to treatment pathways.

In some implementations, the smart synthesizer system 100 includes arole-specific system. Rendition and synthesis is dependent on role of auser accessing the system and method of this system. The databases andrules are defined per roles in order to activate this module.

In some implementations, the smart synthesizer system 100 may includedatabases/datasets, which, further includes symptoms, examinations,vitals, object data, history data, findings' data, and the like. In someimplementations, the smart synthesizer system 100 provides a system andmethod for classifying these databases/datasets into specialty—specificdataset [e.g., cardio, gynecology, and the like] into a constantlyevolving database/dataset based on global, local, and hyperlocalupdates. Furthermore, the smart synthesizer system 100 renders a viewfor a doctor-patient interaction/visit to reduce the time taken for adoctor to view patient summary and document an encounter, place orders,and to aid the doctor with decision-making.

In some implementations, a user may provide user input through anysuitable input device or input mechanism such as but not limited to akeyboard, a mouse, a joystick, a touchpad, a virtual keyboard, a virtualdata entry user interface, a virtual dial pad, a software or a program,a scanner, a remote device, a microphone, a webcam, a camera, afingerprint scanner, a cave, pointing stick, and the like.

In some implementations, the systems and methods can be practiced usingany electronic device. The smart synthesizer 100 includes an electronicdevice that is selected from any device capable of processing orrepresenting data to a user and providing access to a network or anysystem similar to the internet, wherein the electronic device may beselected from but not limited to, personal computers, tablet computers,mobile phones, laptop computers, palmtops, portable media players, andpersonal digital assistants. In an embodiment, the computer readablemedium data storage unit or data storage device is selected from a setof but not limited to USB flash drive (pen drive), memory card, opticaldata storage discs, hard disk drive, magnetic disk, magnetic tape datastorage device, data server and molecular memory.

The process steps, method steps, algorithms or the like may be describedin a sequential order, such processes, methods and algorithms may beconfigured to work in alternate orders. In other words, any sequence ororder of steps that may be described does not necessarily indicate arequirement that the steps be performed in that order. The steps ofprocesses described herein may be performed in any order practical.Further, some steps may be performed simultaneously, in parallel, orconcurrently.

Although a few implementations have been described in detail above,other modifications are possible. For example, while a clientapplication is described as accessing the delegate(s), in otherimplementations the delegate(s) may be employed by other applicationsimplemented by one or more processors, such as an application executingon one or more servers. In addition, the logic flows depicted in theFIGURES do not require the particular order shown, or sequential order,to achieve desirable results. In addition, other actions may beprovided, or actions may be eliminated, from the described flows, andother components may be added to, or removed from, the describedsystems. Accordingly, other implementations are within the scope of thefollowing claims.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular embodiments of particularinventions. Certain features that are described in this specification inthe context of separate embodiments can also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment can also beimplemented in multiple embodiments separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various system modulesand components in the embodiments described above should not beunderstood as requiring such separation in all embodiments, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

Particular embodiments of the subject matter have been described. Otherembodiments are within the scope of the following claims. For example,the actions recited in the claims can be performed in a different orderand still achieve desirable results. As one example, the processesdepicted in the accompanying FIGURES do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

What is claimed is:
 1. A computer-implemented method comprising:identifying profile fields of a patient profile; identifying profiledata items and profile data parameters for each profile field;generating a synthesized context-aware rendition of a patient summaryfrom the profile data items and the profile data parameters, wherein thegenerating includes: determining a context of a patient, wherein thecontext includes at least one of a patient geographical location, acurrent season, or a patient travel history, wherein the context of thepatient is determined in real time based on data received from one ormore devices, and dynamically determining weighting assignments for theprofile data items, and the profile fields in relation to the context;populating the profile fields with the profile data items; rendering, inreal time, the synthesized context-aware rendition of the patientsummary in a context-aware view including an interactive time-line viewfor a doctor-patient interaction, wherein only context relevant data isrendered; capturing real-time data from the doctor-patient interaction;and detecting patterns in the real-time data of the doctor-patientinteraction to iteratively improve the rendering of synthesizedcontext-aware renditions for doctor-patient interactions of patientswith contexts that are similar to the context of the patient.
 2. Thecomputer-implemented method of claim 1, further comprising: in responseto determining the weighting assignments in relation to the context,assigning weights to the profile data items, the profile dataparameters, and knowledge/reference data items.
 3. Thecomputer-implemented method of claim 2, wherein determining theweighting assignments is determined based on a frequency of use, alatest use, determination of various heat maps to understand usage andbehavior, location, specialty, and current condition of the patient. 4.The computer-implemented method of claim 3, further comprising:generating the interactive time-line view for the doctor-patientinteraction from an observation profile.
 5. The computer-implementedmethod of claim 4, wherein the observation profile changes in vitals,inputs, outputs in response to change in dosage of prescribed medicine,in response to change in filtering parameters for labs, vitals, anddiagnostics.
 6. The computer-implemented method of claim 1, furthercomprising: determining a location of a doctor corresponding to thepatient profile assessing a smart synthesizer system, wherein factors indetermining the location of the doctor include care settings, seasons,external conditions, and seriousness of the condition of the patient. 7.A system comprising: one or more computers and one or more storagedevices storing instructions that are operable, when executed by the oneor more computers, to cause the one or more computers to performoperations comprising: identifying profile fields of a patient profile;identifying profile data items and profile data parameters for eachprofile field; generating a synthesized context-aware rendition of apatient summary from the profile data items and the profile dataparameters, wherein the generating includes: determining a context of apatient, wherein the context includes at least one of a patientgeographical location, a current season, or a patient travel history,wherein the context of the patient is determined in real time based ondata received from one or more devices, and dynamically determiningweighting assignments for the profile data items, and the profile fieldsin relation to the context; populating the profile fields with theprofile data items; rendering, in real time, the synthesizedcontext-aware rendition of the patient summary in a context-aware viewincluding an interactive time-line view for a doctor-patientinteraction, wherein only context relevant data is rendered; capturingreal-time data from the doctor-patient interaction; and detectingpatterns in the real-time data of the doctor-patient interaction toiteratively improve the rendering of synthesized context-awarerenditions for doctor-patient interactions of patients with contextsthat are similar to the context of the patient.
 8. The system of claim7, further comprising: in response to determining the weightingassignments in relation to the context, assigning weights to the profiledata items, the profile data parameters, and knowledge/reference dataitems.
 9. The system of claim 8, wherein determining the weightingassignments is determined based on a frequency of use, a latest use,determination of various heat maps to understand usage and behavior,location, specialty, and current condition of the patient.
 10. Thesystem of claim 9, further comprising: generating the interactivetime-line view for the doctor-patient interaction from an observationprofile.
 11. The system of claim 10, wherein the observation profilechanges in vitals, inputs, outputs in response to change in dosage ofprescribed medicine, in response to change in filtering parameters forlabs, vitals, and diagnostics.
 12. The system of claim 7, furthercomprising: determining a location of a doctor corresponding to thepatient profile assessing a smart synthesizer system, wherein factors indetermining the location of the doctor include care settings, seasons,external conditions, and seriousness of the condition of the patient.13. A non-transitory computer-readable medium storing softwarecomprising instructions executable by one or more computers which, uponsuch execution, cause the one or more computers to perform operationscomprising: identifying profile fields of a patient profile; identifyingprofile data items and profile data parameters for each profile field;generating a synthesized context-aware rendition of a patient summaryfrom the profile data items and the profile data parameters, wherein thegenerating includes: determining a context of a patient, wherein thecontext includes at least one of a patient geographical location, acurrent season, or a patient travel history, wherein the context of thepatient is determined in real time based on data received from one ormore devices, and dynamically determining weighting assignments for theprofile data items, and the profile fields in relation to the context;populating the profile fields with the profile data items; rendering, inreal time, the synthesized context-aware rendition of the patientsummary in a context-aware view including an interactive time-line viewfor a doctor-patient interaction, wherein only context relevant data isrendered; capturing real-time data from the doctor-patient interaction;and detecting patterns in the real-time data of the doctor-patientinteraction to iteratively improve the rendering of synthesizedcontext-aware renditions for doctor-patient interactions of patientswith contexts that are similar to the context of the patient.
 14. Thecomputer-readable medium of claim 13, further comprising: in response todetermining the weighting assignments in relation to the context,assigning weights to the profile data items, the profile dataparameters, and knowledge/reference data items.
 15. Thecomputer-readable medium of claim 14, wherein determining the weightingassignments is determined based on a frequency of use, a latest use,determination of various heat maps to understand usage and behavior,location, specialty, and current condition of the patient.
 16. Thecomputer-readable medium of claim 15, further comprising: generating theinteractive time-line view for the doctor-patient interaction from anobservation profile.
 17. The computer-readable medium of claim 16,wherein the observation profile changes in vitals, inputs, outputs inresponse to change in dosage of prescribed medicine, in response tochange in filtering parameters for labs, vitals, and diagnostics. 18.The computer-readable medium of claim 13, further comprising:determining a location of a doctor corresponding to the patient profileassessing a smart synthesizer system, wherein factors in determining thelocation of the doctor include care settings, seasons, externalconditions, and seriousness of the condition of the patient.
 19. Thecomputer-readable medium of claim 13, further comprising: storing, in aninformation database, journal information relating to diseases andtreatment plans for the diseases, and case studies' information relatingto the disease and treatment plans.
 20. The computer-readable medium ofclaim 17, further comprising: displaying, on the interactive time-lineview, the changes in vitals, intake output, labs, or similar data in anempirical format and a predictive format.
 21. The computer-readablemedium of claim 13, wherein the context includes the patientgeographical location.
 22. The computer-readable medium of claim 13,wherein the weighting assignments are based on usage of the profile dataitems and the profile fields.
 23. The computer-readable medium of claim13, wherein the one or more devices includes at least one of an Internetof Things (IoT) device, a wearable device, or other sensor.